Methods and apparatus for controlling provisioning of a wireless communication device

ABSTRACT

Methods and apparatus for controlling provisioning of a wireless communication device in a cellular network may include maintaining, at a network component, a provisioning status database comprising status information corresponding to provisioning in a home location register of one or more wireless communication devices for one or more cellular networks. In addition, the methods and apparatus may include initiating provisioning or de-provisioning of a wireless communication device for a cellular network in the home location register in response to a triggering event.

CLAIM OF PRIORITY UNDER 35 U.S.C. §119

The present Application for Patent claims priority to ProvisionalApplication No. 61/487,655 entitled “Methods and Apparatus forControlling Provisioning of a Wireless Communication Device” filed May18, 2011, and assigned to the assignee hereof and hereby expresslyincorporated by reference herein.

BACKGROUND

The described aspects relate to wireless communications, and moreparticularly to controlling provisioning of one of more wirelesscommunication devices with a home location register (HLR).

The widespread availability of cellular networks, such as 3G and 4Gnetworks worldwide has enabled the proliferation of wireless devicesthat make use of many applications beyond traditional voice services.These devices rely heavily on the “mobility” feature of cellularnetworks, both in-network and also across multiple networks (bothdomestic and international).

One element of the network infrastructure that controls this “roaming”capability is the Home Location Register (HLR). The HLR in conjunctionwith the Authentication Center (AuC or AC) is a database network nodethat stores the identity and subscriber data (credentials) of all theusers of the 3G network. The information stored in the HLR typicallyincludes permanent data such as the IMSI, authentication keys, permittedsupplementary services, and some temporary data. Examples of temporarydata stored in the HLR are the current address of the network nodes(SGSN) serving the subscriber/device that is required to supportmobility.

The information stored in the HLR can be grouped into the followingcategories: Subscriber Data, Security Data and Subscriber Location. MostHLR equipment vendors have integrated the AuC/AC functionality in thesame node as the HLR. In general, the function of the AuC/AC is tomanage the authentication and encryption data over the radio channels.

Since the HLR plays such a critical role in the proper operation of acellular network, it can be implemented as a distributed database forsecurity, reliability and performance reasons. However, logically thereis only one HLR per Mobile Network (PLMN). Moreover, each HLR istypically associated with only a single wireless network carrier. Inorder to enable widespread, pre-provisioned wireless data connectivityin cellular networks worldwide for a variety of wireless devices, devicecredentials must be allocated and programmed into the devices and alsoin the network elements that control access to the cellular networks, inparticular the HLR.

For certain mobile applications or services covering a large number ofdevices worldwide, it may be advantageous to maximize the utilization ofavailable HLR resources. Therefore, there remains a need in the art fordynamically managing the required subscriber data stored in the HLR.

Moreover, newly-developed and large scale mobile data communicationsservice implementations require the pre-provisioning of millions ofwireless devices at the factory, where at some point in time, thedevices will need to be activated to access mobile networks around theworld. In addition, some devices may never require activation whileothers could be de-activated and re-activated multiple times during thelife of the device. Thus, there remains a need in the art forpre-provisioning models that are adapted to new multi-function deviceswith multiple mobile connectivity alternatives.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

One aspect relates to a method of controlling provisioning of a wirelesscommunication device in a cellular network. The method may includemaintaining, at a network component, a provisioning status databasecomprising status information corresponding to provisioning in a homelocation register of one or more wireless communication devices for oneor more cellular networks. The method may also include initiatingprovisioning or de-provisioning of a wireless communication device for acellular network in the home location register in response to atriggering event.

Another aspect relates to at least one processor configured to controlprovisioning of a wireless communication device in a cellular network.The processor may include a first module for maintaining, at a networkcomponent, a provisioning status database comprising status informationcorresponding to provisioning in a home location register of one or morewireless communication devices for one or more cellular networks. Inaddition, the processor may include a second module for initiatingprovisioning or de-provisioning of a wireless communication device for acellular network in the home location register in response to atriggering event.

Another aspect relates to a computer program product. The computerprogram product may include a computer-readable medium including a firstset of codes for causing a computer to maintain, at a network component,a provisioning status database comprising status informationcorresponding to provisioning in a home location register of one or morewireless communication devices for one or more cellular networks. Thecomputer-readable medium may also include a second set of codes forcausing the computer to initiate provisioning or de-provisioning of awireless communication device for a cellular network in the homelocation register in response to a triggering event.

Yet another aspect relates to an apparatus. The apparatus may includemeans for maintaining, at a network component, a provisioning statusdatabase comprising status information corresponding to provisioning ina home location register of one or more wireless communication devicesfor one or more cellular networks. The apparatus may further includemeans for initiating provisioning or de-provisioning of a wirelesscommunication device for a cellular network in the home locationregister in response to a triggering event.

Another aspect relates to an apparatus for controlling provisioning of awireless communication device in a cellular network. The apparatus mayinclude a provisioning status database operable to maintain statusinformation corresponding to provisioning in a home location register ofone or more wireless communication devices for one or more cellularnetworks. The apparatus may also include a home location registermanager component operable to initiate provisioning or de-provisioningof a wireless communication device for a cellular network in the homelocation register in response to a triggering event.

Another aspect relates to a method of controlling provisioning of awireless communication device in a cellular network. The method mayinclude receiving, from a cellular network having a network identifier,a connection request for establishing a connection with a wirelessdevice. In addition, the method may include determining provisioningdata corresponding to a home location register (HLR) to enableconnecting the wireless device to the cellular network based on thenetwork identifier, wherein the provisioning data includes a networkentity identifier of a specific network entity in the cellular networkto use for connecting with the wireless device. The method may furtherinclude providing at least a portion of the provisioning data includingthe network entity identifier to the cellular network.

Another aspect relates to at least one processor configured to controlprovisioning of a wireless communication device in a cellular network.The processor may include a first module for receiving, from a cellularnetwork having a network identifier, a connection request forestablishing a connection with a wireless device. The processor may alsoinclude a second module determining provisioning data corresponding to ahome location register (HLR) to enable connecting the wireless device tothe cellular network based on the network identifier, wherein theprovisioning data includes a network entity identifier of a specificnetwork entity in the cellular network to use for connecting with thewireless device. The processor may additionally include a third modulefor providing at least a portion of the provisioning data including thenetwork entity identifier to the cellular network.

Still another aspect relates to a computer program product. The computerprogram product may include a computer-readable medium including a firstset of codes for causing the computer to receive, from a cellularnetwork having a network identifier, a connection request forestablishing a connection with a wireless device. In addition, thecomputer-readable medium may include a second set of codes for causingthe computer to determine provisioning data corresponding to a homelocation register (HLR) to enable connecting the wireless device to thecellular network based on the network identifier, wherein theprovisioning data includes a network entity identifier of a specificnetwork entity in the cellular network to use for connecting with thewireless device. The computer-readable medium may also include a thirdset of codes for causing the computer to provide at least a portion ofthe provisioning data including the network entity identifier to thecellular network.

Another aspect relates to an apparatus. The apparatus may include meansfor receiving, from a cellular network having a network identifier, aconnection request for establishing a connection with a wireless device.The apparatus may further include means for determining provisioningdata corresponding to a home location register (HLR) to enableconnecting the wireless device to the cellular network based on thenetwork identifier, wherein the provisioning data includes a networkentity identifier of a specific network entity in the cellular networkto use for connecting with the wireless device. In addition, theapparatus may include means for providing at least a portion of theprovisioning data including the network entity identifier to thecellular network.

Yet another aspect relates to an apparatus for controlling provisioningof a wireless communication device in a cellular network. The apparatusmay include a receiver operable to receive, from a cellular networkhaving a network identifier, a connection request for establishing aconnection with a wireless device. The apparatus may also include anactivation engine operable to determine provisioning data correspondingto a home location register (HLR) to enable connecting the wirelessdevice to the cellular network based on the network identifier, whereinthe provisioning data includes a network entity identifier of a specificnetwork entity in the cellular network to use for connecting with thewireless device; and to provide at least a portion of the provisioningdata including the network entity identifier to the cellular network.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements, andin which:

FIG. 1 is an illustration of a connectivity system in accordance with anaspect;

FIG. 2 is a flow chart illustrating a method of controlling provisioningof a wireless communication device in a cellular network in accordancewith another aspect;

FIG. 3 is a flow chart illustrating a method for controllingprovisioning of a wireless communication device in a cellular network inaccordance with yet another aspect;

FIG. 4 is a signaling diagram illustrating subscription creation inaccordance with an aspect;

FIG. 5 is a signaling diagram illustrating first time connectionestablishment in accordance with yet another aspect;

FIG. 6 is a signaling diagram illustrating subsequent connectionestablishment in accordance with an aspect;

FIG. 7 is a signaling diagram illustrating subscription deactivation inaccordance with still another aspect;

FIG. 8 is a signaling diagram illustrating reactivation of a deactivatedsubscription in accordance with an aspect;

FIG. 9 is a signaling diagram illustrating reactivation of an activesubscription in accordance with yet another aspect;

FIG. 10 is a signaling diagram illustrating subscription modification inaccordance with another aspect;

FIG. 11 is a signaling diagram illustrating subscription deletion inaccordance with an aspect;

FIG. 12 an example wireless device operable within the connectivitysystem in accordance with an aspect;

FIG. 13 is an example activation engine operable within the connectivitysystem in accordance with yet another aspect;

FIG. 14 is an illustration of an example system that facilitatescontrolling provisioning of a wireless communication device in acellular network in accordance with an aspect; and

FIG. 15 is an illustration of an example system that facilitatescontrolling provisioning of a wireless communication device in acellular network in accordance with still another aspect.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details.

The described aspects relate to methods and apparatus for implementing“on demand” provisioning and de-provisioning of subscriber data in aHome Location Register (HLR) in a mobile data connectivityinfrastructure. In addition, the described aspects may maximize theutilization of available HLR resources and reduce theoperational/recurring costs associated with the HLR.

In contrast to the current model of subscriber provisioning at thePoint-of-Sale, and the corresponding downstream configuration/update ofthe required network resources (including the HLR), the describedaspects relate to methods and apparatus for pre-provisioning modelsadapted to new multi-function devices with multiple mobile connectivityalternatives that utilizes a more dynamic activation process that mayde-couple the provisioning of subscriber credentials on the device fromthe configuration of certain network resources (e. g., the HLR) untilthe user is ready to activate the device.

In addition, described aspects relate to the methods and apparatus foroptimizing the initial device subscription storage mechanism (andsubsequent subscription modification and/or permanent deletionrequirements) without requiring immediate provisioning of the HLR by theuse of an HLR frontend, an Activation Engine and a Master Database. Bymaximizing the efficiency in the use of HLR resources, the costs ofproviding large-scale service implementations may be reduced.

Referring now to FIG. 1, illustrated is an example connectivity system100 that includes one or more wireless devices 102 communicating withone or more cellular networks 112. Each cellular network 112 may grantor deny access to each wireless device 102 based on on-demandprovisioning of a home location register (HLR) 114 as controlled by anactivation engine 106, which communicates with cellular network 112 viaan HLR frontend component 104. Moreover, activation engine 106 obtainsprovisioning data 122 from an order management component 116, andcontrols the storage of the provisioning data in a master database 110and the selective loading and removing of selected provisioning data fora selected wireless device between master database 110 and HLR 114, asdescribed herein.

In one aspect, which should not be construed as limiting, the describedaspects may efficiently manage usage of HLR 114 for a plurality ofwireless communication devices 102, such as computer devices withwireless modems produced by one or more device suppliers 108, where manyof the wireless devices 102 may have different levels of interactionwith cellular networks 112. As such, rather than pre-load HLR 114 withrecords including the provisioning data for each wireless device andeach cellular network, some of which may be rarely or never needed, thedescribed aspects include activation engine 106 to manage storage of theprovisioning data in master database 110 until a corresponding wirelessdevice 102 requests connectivity to cellular network 112, therebytriggering loading of the corresponding provisioning data into HLR 114.Further, activation engine 106 manages the removal of provisioning datafrom HLR 114 based on one or more conditions, such as an availableprovisioning data storage capacity relative to a threshold, or aninactivity of the wireless communication device on the cellular networkrelative to an inactivity threshold level.

In another aspect, which should not be construed as limiting, thedescribed aspects may conveniently manage usage of HLR 114 for aplurality of cellular network carriers 120. In other words, thedescribed aspects provide a universal HLR 114 that operates for morethan one wireless network carrier. For example, in the scenariodescribed above, device suppliers may obtain provisioning data from oneor more participating wireless network carriers corresponding to one ormore cellular networks operated by each carrier. Accordingly, thedescribed aspects avoid the need, by the device supplier, tospecifically pre-load or pre-associate each wireless communicationdevice 102 with only a given one of the wireless network carriers. Inparticular, activation engine 106 has access to master database 110 andthe plurality of provisioning data, which may correspond to a pluralityof different wireless network carriers and corresponding cellularnetworks, for each wireless communication device 102. As such,activation engine 106 can load into HLR 114, in an on-demand fashion,any of the provisioning data for any of the cellular networkscorresponding to any of the wireless network carriers, thereby providingHLR 114 with the capability of universal wireless network carriersupport,

Thus, connectivity system 100 allows wireless device 102 to connect tocellular networks 112 in various locations through on-demandprovisioning home location register 114 with the provisioning data thatallows wireless device 102 to connect to cellular network 112.

In an aspect, which should not be construed as limiting, networkprovisioning scenarios may include an order management component 116that may be used by cellular networks 120, e.g., operators, to create anew customer account or subscription, or to update an existing accountor subscription with new information related to the products and/orservices available to a specific wireless communication devicecorresponding to a customer or subscriber.

For example, in an aspect, order management component 116 may obtainnetwork provisioning data 122, which may be used to delete, modify anddisplay the different network services such as Data, Voice, GPRS, VMS,MMS, Conferencing, Call Waiting, Call Forwarding, etc., for a specificwireless communication device, e.g., associated with a customer and/orsubscriber account.

As such, network provisioning data 122 may be utilized in the process ofactivating and de-activating customers, e.g., wireless device 102, sothat they can use a mobile network.

In one aspect, which should not be construed as limiting, once a new‘Order’ has been entered, e.g., based on device supplier producingwireless communication device 102 having cellular connectivity supportedby one or more participating wireless network carriers, order managementcomponent 116 initiates the network provisioning. For example, ordermanagement component 116 may forward provisioning data 122 for one ormore wireless communication devices 102 to activation engine 106.Subsequently, activation engine 106 may generate network messages todirect one or more network elements that are responsible forprovisioning different network services. The main mobile networkelements that have to be provisioned in order to create a new customeraccount are the Home Location Register (HLR) 114 and/or theAuthentication Center (AuC) 124.

As explained previously, the HLR 114 stores details of each wirelesscommunication device, e.g., corresponding to a subscriber that isauthorized to use the network. For example, HLR 114 may utilize a deviceidentifier, such as an International Mobile Subscriber Identity numberor IMSI to identify a record or an account, including provisioning data,for each wireless communication device. Once a new account has beenprovisioned onto the HLR, the HLR works in tandem with the AuC 124 toverify that subscribers are allowed to access and use the services ofthe network. In addition, other parameters related to packet dataservices may also be part of the provisioning process.

As noted above, rather than directly provisioning HLR 114 upon receiptof provisioning data 122, activation engine 106 instead storesprovisioning data 122 in master database 110 to conserve usage of theresources, e.g., the provisioning data record storage capacity, of HLR114 until such resources are actually needed by wireless communicationdevice 102. Activation engine 106 may include any mobile or fixedserver/computing device connected to a network.

For instance, upon usage, wireless device 102 may have a connectionmanager component 10 operable to determine the available networks forconnection with wireless device 102. Wireless device 102 may include anymobile, portable computing or communications device, such as a cellulardevice, that may connect to an access network. As noted, in an aspectwireless device 102 may be a computer having a cellular modem, however,in other aspects wireless device 102 may include, but is not limited to,a cellular telephone, a navigation system, a computing device, a camera,a PDA, a music device, a gaming device or a handheld device havingwireless connection capability, among other devices. In addition,connection manager 10 may be further operable to send connectionrequests to connect wireless device 102 with the one or more availablenetworks. Connection manager component 10 may include a selectioncomponent 12 operable to determine which networks are available forconnection with wireless device 102. In an aspect, selection component12 may determine that access networks, such as Wi-Fi are not availablefor connection with wireless device 102 and may provide a list ofcellular networks 112 that are available for connection with wirelessdevice 102. Selection component may select one of the available cellularnetworks 112 for connection with wireless device 102.

Alternatively, or in addition, selection component may have one or moreuser interfaces 18 to prompt a user to select one of the availablenetworks for attempting to provide a connection for wireless device 102.For example, a list of available cellular networks may be displayed on auser interface. Wireless device 102 may receive input from a user with aselection of one of the available networks.

Selection component may also interface with an approved network datacomponent 14 to compare the list of available cellular networks with alist of approved networks prior to selecting one of the availablenetworks for connection. The list of approved networks may be providedby device supplier 108 upon manufacturing of wireless device 102, or viaperiodic inquires from wireless device 102 to a network component.

For example, in an aspect, this list of approved networks and/orprovisioning data 122 may be modified and/or updated by device supplier108 and/or wireless network carriers 120. For example, device supplier108 may engage new wireless network carriers 120, and/or may ceaserelationships with previously used wireless network carriers, orexisting provisioning data 122 for a wireless network carrier or acorresponding cellular network may be changed. As such, in an aspect,connection manager 10 may interface with the device supplier 108 and/oractivation engine 106 to determine whether the list of approved networkshas been updated and may receive any modifications and/or updates forthe list of approved networks. It should be appreciated the list ofapproved network data may be in sync with the network data andprovisioning data in the master database 110. In an aspect, approvednetwork data component 14 may communicate with HLR 114, master database110 and/or activation engine 106 to keep the information delivered toconnection manager 10, the HLR 114, and the master database 110 in sync.For example, when an update is received and/or occurs to information atthe connection manager 10, the approved network data component 14 maytrigger the corresponding updates towards the HLR 114, master database110, and/or the activation engine 106. Moreover, it should beappreciated that connection manager 10 may obtain some portion of theprovisioning data 122 corresponding to each approved network, forexample, to enable wireless communication device 102 to initiallyestablish communication with the given cellular network and requestconnectivity.

Connection manager 10 may further include a connection request component16 operable to send a connection request to the selected cellularnetwork 112 to request connectivity with the selected cellular network112.

Cellular network 112 may communicate with HLR frontend component 104,which may forward the connection request to activation engine 106 andhold the connection request from cellular network 112 until receiving aconnection decision, e.g., an acknowledgement to allow connectivity or adenial of connectivity, from activation engine 106.

Activation engine 106 may receive the connection request from HLRfrontend component 104 and may determine whether wireless device 102 mayproperly connect to cellular network 112, e.g., based on subscriptioninformation, and whether wireless device 102 is already provisioned inHLR 114. In other words, in an aspect, activation engine 106 istriggered to control provisioning of HLR 114 for wireless device 102 byan attempt by the wireless device 102 to connect to the cellular network112. In an aspect, the connection request from wireless device 102 mayinclude a device identifier, such as the IMSI, as well as a networkidentifier, such as an identifier of cellular network 112.

For example, if the wireless device 102 is a subscriber to cellularnetwork 112 and already has a record with corresponding provisioningdata stored in HLR 114, then activation engine 106 may acknowledge theconnection request from HLR frontend 104, and wireless device 102 mayconnect with cellular network 112.

On the other hand, if the wireless device 102 is a valid subscriber forcellular network 112 but is not already provisioned in HLR 114, thenactivation engine 106 may communicate with master database 110 toprovision wireless device 102 in HLR 114. As noted, HLR 114 may includea plurality of provisioning data for a plurality of wirelesscommunication devices. As such, activation engine 106 may obtain, frommaster database 110, a subset of the plurality of provisioning datacorresponding to the device identifier and the network identifier andmay send a provisioning message with the obtained subset of provisioningdata to initiating adding a record to HLR 114.

In an aspect, for example, if a device has been inactive and removedfrom the HLR, re-provisioning of that device may be possible and may betriggered by the device attempting to use the cellular network. Inaddition, if a previously-activated device requests a connection to adifferent network (e.g., in a different country), the HLR may need to bere-provisioned to reflect the provisioning data 122, e.g., thesubscription information, relevant for the new network (e.g., accesspoint name “APN”).

In an optional aspect, master database 110 may include state data 28associated with the provisioning data for one or more networks. Statedata may include, but is not limited to, state information provided byHLR 114 so that if a wireless device is re-provisioned to an HLR theprevious state data from the HLR may be included with the provisioningdata.

Activation engine 106 may further be operable to remove, de-activate,and/or de-provision wireless device 102 from HLR 114. Wireless device102 may need to be de-activated from the HLR, for example, when thenumbers of records in the HLR reach and/or exceed a threshold level ofallowed records. For example, in an aspect that should not be construedas limiting, the threshold level may be a set percentage of totalcapacity, or may be a figure determined based on the time it takes todelete an existing record to make room for a new record, e.g., in orderto avoid or minimize latency in adding the new record caused by the timeit takes to remove the existing record to clear space for the newrecord. In addition, when a previously configured device that has notbeen in use for a pre-determined period of time and/or will no longer bein use (lost, stolen, discarded, etc. . . ), activation engine 106 maycontrol de-activation of the device may occur from the HLR. In someaspects, de-activation may be performed in a manner that allowssubsequent re-activation of the same device. By de-activating devicesfrom the HLR, the use of available HLR resources, e.g., provisioningrecord-storing capacity, may be maximized.

Referring now to FIG. 2, a method 200 for controlling provisioning of awireless communication device in a cellular network in accordance withan aspect includes, at 202, maintaining, at a network component, aprovisioning status database comprising status information correspondingto provisioning in a home location register of one or more wirelesscommunication devices for one or more cellular networks. For example,activation engine 106 (FIG. 1) may include a provisioning statusdatabase 22 (FIG. 1). The provisioning status database 22 may include,but is not limited to, a device identifier field and a networkidentifier field, among other database fields. In an aspect, the homelocation register may be configured, for example, to store a pluralityof provisioning data corresponding to a plurality of different networkcarriers. The method may optionally include storing, in a masterdatabase, subscription data corresponding to the wireless communicationdevice. For example, activation engine 106 (FIG. 1) may communicate witha master database 110 (FIG. 1) and store subscription data correspondingto wireless device 102 (FIG. 2).

The method may also include, at 204, initiating provisioning orde-provisioning of a wireless communication device for a cellularnetwork in the home location register in response to a triggering event.The triggering event may be based upon receiving signaling correspondingto a request for the wireless communication device to connect to thecellular network. The signaling may include, but is not limited to, adevice identifier corresponding to the wireless communication device anda network identifier corresponding to the cellular network, wherein thesignaling corresponding to the request comprises the triggering event.

In addition, the triggering event may be based upon an occurrence of ade-provisioning condition. Determining the occurrence of thede-provisioning condition may further include, for example, determiningthat a capacity for storing provisioning records in the home locationregister has reached a capacity threshold level. In another aspect,determining the occurrence of the de-provisioning may further includedetermining that inactivity of the wireless communication device on thecellular network has reached an inactivity threshold level. Determiningthe occurrence of the de-provisioning condition may also includereceiving signaling to release a connection with the cellular network,such as a connection release to disconnect from a cellular network.

The initiating provisioning or de-provisioning may further comprise, forexample, transmitting a de-provisioning message destined for the homelocation register, and the de-provisioning message initiates removingfrom the home location register a provisioning record comprisingprovisioning data for the wireless communication device on the cellularnetwork. For example, activation engine 106 may send a provisioningmessage 24 (FIG. 1) to provision a record in HLR 114 (FIG. 1) with thesubscription data for wireless device 102 in response to a triggeringevent. In addition, activation engine 106 may send a de-provisioningmessage 26 (FIG. 1) to remove a provisioning record from HLR 114 inresponse to a triggering event.

In addition, the method may optionally include receiving provisioningdata for the wireless communication device and transmitting theprovisioning data to a master database for storage until occurrence ofthe triggering event that causes initiating of the provisioning at thehome location register. For example, activation engine 106 maycommunicate with a master database 110 and store the provisioning datafor wireless device 102. In an aspect, transmitting at least a portionof the provisioning data to the wireless communication device may be inresponse to a provisioning data query received from the wireless device.

Referring now to FIG. 3, a method 300 for controlling provisioning of awireless communication device in a cellular network in accordance withan aspect includes, at 302, receiving from a cellular network having anetwork identifier, a connection request for establishing a connectionwith a wireless device. In an aspect, the connection request may alsoinclude a wireless device identifier, such as an IMSI. For example,activation engine 106 (FIG. 1) may receive a connection request with anIMSI of wireless device 102 (FIG. 1) from cellular network 112 (FIG. 1)to establish a connection with wireless device 102.

The method may also include, at 304, determining provisioning datacorresponding to a home location register to enable connecting thewireless device to the cellular network based on the network identifier,wherein the provisioning data includes a network entity identifier of aspecific network entity in the cellular network to use for connectingwith the wireless device. Provisioning data may include, but is notlimited to, the IMSI of the wireless device, the cellular networkidentification, and a specific network entity (e.g., APN) for providingthe services via the cellular network. For example, activation engine106 may determine provisioning data for HLR 114 to establish aconnection between cellular network 112 and wireless device 102.

In addition, the method may include, at 306, providing at least aportion of the provisioning data including the network entity identifierto the cellular network. In an aspect, the network entity identifier(e.g., APN) may identify a local network specific node in the cellularnetwork that is defined for providing services for wireless devicesprovisioned to the HLR. For example, activation engine 106 may forwardthe network entity identifier to cellular network 112 to use whenestablishing a connection with wireless device 102.

The signaling flows for the different events related to devicesubscription creation and activation, and the corresponding systemmodules involved in the process of on-demand provisioning the HLR, areillustrated in FIGS. 4-11. The following terms may be referenced inconnection with and/or illustrated in the following figures: mobilecountry code (MCC), mobile network code (MNC), key, e.g., acryptographic key (K), and access point name (APN).

Referring now to FIG. 4, illustrated is a signaling diagram 400 forsubscription creation in accordance with an aspect. Signal flow 400describes an initial entry into the master database of the devicesubscription data (e.g., IMSI, Keys, and Network info—MCC, MNC, APN),while not involving the HLR directly. The master database will containall the required provisioning data for all devices that have beenpre-provisioned at the factory. At 402, activation engine 106 mayreceive a create subscription message from the order managementcomponent 116. The create subscription message may include a list ofallowed and/or approved networks and respective APNs that a wirelessdevice may access. In addition, the create subscription message mayinclude a list of network services that the wireless device may use. Inan aspect, the create subscription message may include subscriptiondata, such as but not limited to, the IMSI of a wireless device, a key(K), network identification information (e.g., MCC and MNC) for thenetworks the wireless device may access, and access point names (APN)within the networks that the wireless device may access. For example,order management component 116 may obtain a list of approved networksfor use with wireless device 102 (FIG. 1), for example, from a devicesupplier 108 (FIG. 1) and/or a cellular network carrier 120 (FIG. 1)upon, for example, manufacturing of wireless device 102.

Next, at 404, activation engine 106 may forward the receivedsubscription data sent with the create subscription message to masterdatabase 110. Master data base 110 may add a record with thesubscription data for wireless device 102 to the master database 110.For example, the master database 110 may add the list of allowed and/orapproved networks and respective APNs that the wireless device mayaccess. In addition, the master database may add the network servicesthat the wireless device may use.

Referring now to FIG. 5, illustrated is a signaling diagram 500 for afirst time connection establishment in accordance with yet anotheraspect. Signaling diagram 500 illustrates a first activation eventgenerated by a device itself that will trigger a provisioning of theHLR, using information already available in the master database. Theinteraction between the HLR frontend, the Activation Engine and theMaster Database, ensures that the new device is provisioned into the HLRonly as needed to ensure the most optimized use of HLR resources.

At 502, wireless device 102 may attempt to connect to cellular network112 by sending a connection request to a selected cellular network 112.For example, a connection request component 16 (FIG. 1) on wirelessdevice 102 may send a connection request to the selected cellularnetwork 112 requesting connectivity with the selected cellular network112. The connection request may include the IMSI of wireless device 102and may identify a record or an account for wireless device 102,including provisioning data for the wireless device. In addition, theconnection request may include a network identifier corresponding to theselected cellular network 112.

In an aspect, the cellular network may be selected from a list ofapproved networks. The list of approved networks may include, but arenot limited to, a list of networks provided by a device supplier uponmanufacturing of the wireless device and/or a list of networks providedby a network component (e.g., an activation engine or a devicesupplier). It should be appreciated that the wireless device may obtainsome portion of the provisioning data corresponding to each approvednetwork, for example, to enable the wireless communication device toinitially establish communication with the given cellular network andrequest connectivity.

At 504, the HLR frontend 104 may receive the connection requestforwarded from cellular network 112. The connection request may includethe IMSI of wireless device 102 along with the cellular networkidentification (e.g., MCC and MNC) for cellular network 112.

At 506, the HLR frontend 104 may hold the connection request fromcellular network 112 until receiving a connection decision fromactivation engine 106. For example, HLR frontend 104 may hold theconnection request forwarded from cellular network 112 until theactivation engine 106 sends an acknowledgement to allow connectivityand/or a denial of connectivity.

Next, at 508, the HLR frontend 104 may send a connection indicationmessage to the activation engine 106. The connection indication messagemay include, but is not limited to, the IMSI of wireless device 102 andthe cellular network identification (e.g., MCC and MNC) for cellularnetwork 112.

At 510, activation engine 106 may determine whether wireless device 102is provisioned in HLR 114. For example, activation engine 106 maydetermine whether the subscription information associated with the IMSIof wireless device 102 is currently provisioned in HLR 114. Theactivation engine may, for example, compare the IMSI and the cellularnetwork identification with the provisioning data stored in the HLR. Ifthere is no match between the IMSI of wireless device and/or thecellular network identification of cellular network 112 and theprovisioning data stored in the HLR, the activation engine may determinethat the subscription information is not already provisioned in the HLR.

When activation engine 106 determines that wireless device 102 is notprovisioned in HLR 114, at 512, activation engine 106 may fetch thesubscription information for wireless device 102 from the masterdatabase 110. For example, activation engine 106 may communicate withmaster database 110 and obtain, from master database 110 having aplurality of provisioning data for a plurality of wireless communicationdevices, provisioning data 122 (FIG. 1) corresponding to the IMSI ofwireless device 102 and the cellular network identification of cellularnetwork 112.

Next, at 514, activation engine 106 may send a provisioning message 24(FIG. 1) to HLR 114 to initiate adding a record to HLR 114 with theprovisioning data for wireless device 102. The provisioning message mayinclude provisioning data, such as but not limited to, the IMSI of thewireless device, the cellular network identification, and a specificnetwork entity (e.g., APN) for providing the services via the cellularnetwork. In some cases of this aspect, the provisioning data, and inparticular, the specific network entity for providing services may bebased on the cellular network identity of the cellular network that thewireless device is attempting to access. Alternatively, or in addition,the provisioning data, and in particular, the specific network entityfor providing services may be based on the device identity of thewireless device that is attempting to access the cellular network. Thus,the activation engine may be triggered to provision the HLR for thewireless device by an attempt of the wireless to connect to the cellularnetwork.

At 516, activation engine 106 may receive an acknowledgement from HLR114 that a provisioning record with the provisioning data for wirelessdevice 102 was added to the HLR 114. In an aspect, activation engine 106may include a provisioning status database 22 (FIG. 1) with a deviceidentifier field and a network identifier field. Upon receiving anacknowledgement from HLR 114 that the provisioning data was added to theHLR 114, activation engine 106 may update the provisioning statusdatabase 22 to indicate that the provisioning data for wireless device102 is currently provisioned to HLR 114. For example, activation engine106 may update the device identifier field of the provisioning statusdatabase 22 to include the IMSI of wireless device 102. In addition,activation engine 106 may update the network identifier field of theprovisioning status database 22 to include the network identifierinformation for cellular network 112. It should be noted that the HLRmay store a plurality of provisioning data corresponding to a pluralityof different network carriers.

At 518, the HLR frontend 104 may receive a connection decision fromactivation engine 106 with an acknowledgment to allow connectivity.Next, at 520, HLR frontend 104 may send a connect message to HLR 114requesting connectivity to cellular network 112.

It should be noted that in some aspects, at 522, a subsequent responsemessage from the HLR back to the cellular network may includeprovisioning data that includes a network entity identifier of aspecific network entity, e.g., APN, to use for connecting with thewireless device by the cellular network. For example, the specificnetwork entity may include a local network specific gateway node in thecellular network that is defined for providing services via the cellularnetwork for wireless devices provisioned to the HLR.

Referring now to FIG. 6, illustrated is signaling diagram 600 forsubsequent connection establishment in accordance with an aspect.Signaling flow 600 illustrates the interaction between a device, the HLRfrontend and the Activation Engine to determine if the device is alreadyactivated and provisioned in the HLR. It should be noted that signals602-610 may be similar to the signals as described above in regards to502-510. At 602, wireless device 102 may attempt to connect to cellularnetwork 112 by sending a connection request to cellular network 112.Next, at 604, HLR frontend 104 may receive the connection requestforwarded from cellular network 112. At 606, the HLR frontend 104 mayhold the connection request from cellular network 112 until receiving aconnection decision from activation engine 106 (e.g., an acknowledgementto allow connectivity and/or a denial of connectivity). Further, at 608,the HLR frontend 104 may send a connection indication message includingthe IMSI of wireless device 102 and the cellular network identification(e.g., MCC and MNC) for cellular network 112 to activation engine 106.

At 610, activation engine 106 may determine whether wireless device 102is provisioned in HLR 114. For example, activation engine 106 maydetermine whether the subscription information for the requestedcellular network 112 associated with the IMSI of wireless device 102 iscurrently provisioned in HLR 114. Activation engine 106 may include aprovisioning status database 22 (FIG. 1) which may indicate whether awireless device is provisioned in HLR 114. The activation engine may,for example, compare the received IMSI with the device identifier fieldof the provisioning status database. In addition, the activation enginemay compare the received cellular network identification with thenetwork identifier field of the provisioning status database. When theIMSI and the cellular network identification matches provisioning datastored in the device identifier field and network identifier filed ofthe provisioning status database, the activation engine may determinethat the subscription information for the cellular network is alreadyprovisioned in the HLR.

Next, at 612, activation engine 106 may send a connection decision tothe HLR frontend 104 with an acknowledgement to allow connectivity tocellular network 112. At 614, the HLR frontend 104 may send a connectmessage to HLR 114 requesting connectivity with cellular network 112.

Referring now to FIG. 7, illustrated is signaling diagram 700 forsubscription deactivation in accordance with an aspect. Signalingdiagram 700 illustrates the Activation Engine determining, based on aset of pre-arranged criteria, if a device needs to be de-activated andthe configuration data of the device removed from the HLR. At 702,activation engine 106 may determine that a deactivation and/or ade-provisioning condition occurred for an IMSI of a wireless device.Determining an occurrence of a deactivation and/or a de-provisioningcondition may include, for example, determining that a capacity forstoring provisioning records in the home location register has reached acapacity threshold level. For example, in an aspect that should not beconstrued as limiting, the capacity threshold level may be a setpercentage of total capacity, or may be a figure determined based on thetime it takes to delete an existing record to make room for a newrecord, e.g., in order to avoid or minimize latency in adding the newrecord caused by the time it takes to remove the existing record toclear space for the new record. In another aspect, determining theoccurrence of the deactivation and/or de-provisioning condition mayinclude determining that inactivity of the wireless communication deviceassociated with the IMSI on the cellular network has reached aninactivity threshold level. Further, for example, the deactivationand/or de-provisioning condition may occur when a previously configureddevice has not been in use for a pre-determined period of time and/orwill no longer be in use (lost, stolen, discarded, etc. . . ).

At 704, activation engine 106 may send a de-provisioning message 26(FIG. 1) destined for HLR 114. The de-provisioning message may includethe IMSI of the wireless device associated with the subscriptioninformation. In an aspect, the de-provisioning message may initiate theremoval from the home location register a provisioning record comprisingprovisioning data for the wireless communication device associated withthe IMSI on the cellular network. Thus, the activation engine may betriggered to de-provision the HLR for the wireless device by theoccurrence of a deactivation and/or de-provisioning condition.

Next, at 706, activation engine 106 may receive an acknowledgment fromHLR 114 that the provisioning record associated with the IMSI of thewireless device has been removed from HLR 114. For example, activationengine 106 may include a provisioning status database 22 (FIG. 1) whichmay indicate whether a wireless device is provisioned in HLR 114. Thus,when activation engine 106 receives an acknowledgement from HLR 114 thatthe provisioning record associated with wireless device 102 (FIG. 1) hasbeen removed from HLR 114, activation engine 106 may update theprovisioning status database 22 to indicate that the provisioning recordassociated with wireless device 102 is not currently provisioned in HLR114. In some aspects, de-activation may be performed in a manner thatallows subsequent re-activation of the same device. By de-activatingdevices from the HLR, the use of available HLR resources, e.g.,provisioning record-storing capacity, may be maximized

Illustrated in FIGS. 8 and 9 are the cases where thepreviously-activated device may need to be re-activated, either becauseit was de-activated based on the criteria used by the Activation Engineand its configuration information removed from the HLR, or because thedevice is active but it is attempting to connect to a different network(e.g., in a different country).

Referring now to FIG. 8, illustrated is signaling diagram 800 forreactivation of a deactivated subscription in accordance with an aspect.Signaling diagram 800 illustrates an aspect where the device has beende-activated, as illustrated in FIG. 7, and the device configuration wasremoved from the HLR. As illustrated in FIG. 8, re-activation willre-provision the HLR with the appropriate data.

At 802, the HLR frontend 104 may hold the connection request receivedfrom cellular network 112 until receiving a connection decision fromactivation engine 106 (e.g., an acknowledgement to allow connectivityand/or a denial of connectivity). At 804, the HLR frontend 104 mayforward the connect indication message to activation engine 106. Asdiscussed above in FIG. 5, the connect indication message may includethe IMSI of wireless device 102 and the network identificationinformation (e.g., MCC1 and MNC1) for cellular network 112.

Next, at 806, activation engine 106 may determine whether wirelessdevice 102 is provisioned in HLR 114. In an aspect, activation engine106 may include a provisioning status database 22 (FIG. 1) which mayindicate whether wireless device 102 is already provisioned in HLR 114.When wireless device 102 is not currently provisioned in HLR 114, theprovisioning status database 22 indicates that wireless device 102 isnot provisioned in HLR 114. The provisioning data associated with thewireless device may have been de-activated from the HLR, as illustratedin FIG. 7.

Upon determining that the subscription information for wireless device102 is not currently provisioned in HLR 114, at 808, activation engine106 may fetch the subscription information for wireless device 102 fromthe master database 110. For example, activation engine 106 maycommunicate with master database 110 and obtain, from master database110, provisioning data 122 (FIG. 1) corresponding to the IMSI ofwireless device 102 and the cellular network identificationcorresponding to cellular network 112.

Next, at 810, activation engine 106 may send a provisioning message 24(FIG. 1) with the subscription information to re-provision thesubscription information for wireless device in HLR 114. Theprovisioning message may include provisioning data, such as but notlimited to, the IMSI of the wireless device, the cellular networkidentification, and a specific network entity (e.g., APN) for providingthe services via the cellular network. In some cases of this aspect, theprovisioning data, and in particular, the specific network entity forproviding services may be based on the cellular network identity of thecellular network that the wireless device is attempting to access.Alternatively, or in addition, the provisioning data, and in particular,the specific network entity for providing services may be based on thedevice identity of the wireless device that is attempting to access thecellular network.

At 812, activation engine 106 may receive an acknowledgement from HLR114 that a provisioning record with the provisioning data for wirelessdevice 102 was added to HLR 114. In an aspect, the activation engine 106may update the provisioning status database 22 to indicate that theprovisioning data associated with wireless device 102 is currentlyprovisioned to HLR 114.

At 814, the HLR frontend 104 may receive a connection decision (e.g., anacknowledgment to allow connectivity) from activation engine 106. Next,at 816, the HLR frontend 104 may send a connect message to HLR 114requesting connectivity to cellular network 112.

Referring now to FIG. 9, illustrated is signaling diagram 900 forreactivation of an active subscription in accordance with an aspect.Signaling diagram 900 illustrates an aspect where a previously activateddevice will need to be re-provisioned in the HLR with a new profile forthe new network. It should be appreciated that, in an aspect, only oneprovisioning record is maintained at the HLR per device.

At 902, the HLR frontend 104 may hold the connection request receivedfrom cellular network 2 until receiving a connection decision fromactivation engine 106 (e.g., an acknowledgement to allow connectivityand/or a denial of connectivity). At 904, the HLR frontend 104 mayforward the connect indication message to the activation engine 106. Theconnect indication message may include the IMSI of wireless device 102requesting the connection to cellular network 2 and the networkidentification information for cellular network 2 (e.g., MCC2 and MNC3).

Next, at 906, activation engine 106 may determine that wireless device102 is provisioned to connect via another cellular network. For example,activation engine 106 may include a provisioning status database 22(FIG. 1) which may determine that wireless device 102 is alreadyprovisioned in HLR 114 for another cellular network, e.g., cellularnetwork 112. The activation engine may, for example, compare thereceived IMSI with the device identifier field of the provisioningstatus database. In addition, the activation engine may compare thereceived cellular network identification with the network identifierfield of the provisioning status database. In an aspect, when the deviceidentifier field matches the IMSI but the received cellular networkidentification information (e.g., MCC2 and MNC3) does not match thecellular network identification information (e.g., MCC1 and MNC1) in thenetwork identifier field, the activation engine may determine that thewireless device is provisioned to connect to another cellular networkinstead of cellular network 2.

Upon the activation determining that the subscriber is provisioned toconnect to another cellular network, at 908, the activation engine 106may send a de-provisioning message 26 (FIG. 1) to HLR 114 tode-provision the subscription information from HLR 114. Thede-provisioning message may include, for example, the IMSI of wirelessdevice 102 associated with the subscription information in the HLR.

At 910, activation engine 106 may receive an acknowledgement from HLR114 that a provisioning record with the subscription informationassociated with the IMSI of wireless device 102 has been removed fromHLR 114. In some aspects, as discussed above in FIG. 7, de-provisioningthe subscription information from the HLR may be performed in a mannerthat allows subsequent re-activation of the same device. In addition,the activation engine may update the provisioning status database toindicate that the subscription information for wireless device 102 hasbeen removed from HLR 114.

Next, at 912, activation engine 106 may fetch the subscriptioninformation for wireless device 102 associated with cellular network 2from master database 110. It should be noted that the master databasemay include subscription information for each cellular network that awireless device is capable of accessing. Therefore, the activationengine may receive different subscription information for a wirelessdevice from the master database depending on which cellular network thewireless device is attempting to connect with.

At 914, activation engine 106 may send a provisioning message 24(FIG. 1) to HLR 114 to provision HLR 114 with the subscriptioninformation for wireless device 102. The provisioning message mayinclude provisioning data, such as but not limited to, the IMSI of thewireless device, the cellular network identification for cellularnetwork 2 (e.g., MCC2 and MNC3), and a specific network entity (e.g.,APN_Y) for providing the services via cellular network 2. It should benoted that, in an aspect, only one provisioning record is maintained atthe HLR per wireless device. In addition, the provisioning recordsmaintained at the HLR may dynamically change based upon what cellularnetwork the wireless device is connecting with.

Next, at 916, activation engine 106 receives an acknowledgment from HLR114 that a provisioning record with the provisioning data was added tothe HLR 114. In an aspect, upon receiving an acknowledgement from HLR114 that the provisioning data was added to the HLR 114, activationengine 106 may update the provisioning status database 22 to indicatethat the provisioning data is currently provisioned to HLR 114. Forexample, activation engine 106 may update the device identifier field ofthe provisioning status database 22 to include the IMSI of wirelessdevice 102. In addition, activation engine 106 may update the networkidentifier field of the provisioning status database 22 to include thenetwork identifier information for cellular network 2.

At 918, the HLR frontend 104 may receive a connection decision fromactivation engine 106 with an acknowledgment to allow connectivity. At920, the HLR frontend 104 may send a connect message to HLR 114requesting connectivity to cellular network 2.

Referring now to FIG. 10, illustrated is signaling diagram 1000 forsubscription modification in accordance with an aspect. Signalingdiagram 1000 illustrates an aspect that does not involve the HLR butrelies on the Activation Engine and the Master Database to modify thedevice subscription information. The modification to the devicesubscription can occur either before or after the First Activationoccurs.

At 1002, the activation engine 106 may receive a modify subscriptionmessage from the order management component 116. The modify subscriptionmessage may include updated network services such as Data, Voice, GPRS,VMS, MMS, Conferencing, Call Waiting, Call Forwarding, etc., for awireless device. In addition, the modify subscription message mayinclude an updated list of allowed and/or approved networks andrespective APNs that a wireless device may access. The list of approvednetworks and/or provisioning data may be modified and/or updated by adevice supplier and/or a wireless network carrier. For example, devicesupplier 108 (FIG. 1) may engage new wireless network carriers 120 (FIG.1), and/or may cease relationships with previously used wireless networkcarriers, or existing provisioning data 122 (FIG. 1) for a wirelessnetwork carrier or a corresponding cellular network may be changed.

In an aspect, the modify subscription message may include, but is notlimited to, the IMSI of a wireless device, a key (K), updated networkidentification information (e.g., MCC and MNC), and updated access pointnames (APN). For example, order management component 116 may obtain anupdated list of approved networks for use with wireless device 102 (FIG.1), for example, from a device supplier 108 and/or a cellular networkcarrier 120 (FIG. 1). The updated list of approved networks may be usedto modify the subscription data associated with wireless device 102,e.g., associated with a customer and/or subscriber account.

Next, at 1004, activation engine 106 may forward the received modifysubscription message to the master database 110. In an aspect,activation engine 106 may forward the received modify subscriptionmessage to master database 110 to update the subscription datacorresponding to the wireless communication device associated with theIMSI included in the modify subscription message. The master databasemay modify the subscription data to include the updated list of allowedand/or approved networks and respective APNs that a wireless device mayaccess. In addition, the master database may modify the subscriptiondata to include updated network services provided to the wirelessdevice.

Referring now to FIG. 11, illustrated is signaling diagram 1100 forsubscription deletion in accordance with an aspect. Signaling diagram1100 illustrate an aspect which involves the removal of the devicesubscription from the Master Database.

At 1102, activation engine 106 may receive a delete subscription messagefrom the order management component 116. For example, order managementcomponent 116 may send a delete subscription message including an IMSIof a wireless device to activation engine 106 to remove the subscriptiondata associated with the wireless device from the master database 110.Removal of the device subscription may occur, for example, as a finalremoval of the device data from the system when no further use isexpected.

At 1104, activation engine 106 may forward the received deletesubscription message to the master database 110. For example, the masterdatabase 110 may delete the subscription data associated with the IMSIof the wireless device.

Referring now to FIG. 12, illustrated is an example wireless device 102operable within the connectivity system in accordance with an aspect. Inone aspect, wireless device 102 may include a processor 80 for carryingout processing functions associated with one or more of components andfunctions described herein. Processor 80 can include a single ormultiple set of processors or multi-core processors. Moreover, processor80 can be implemented as an integrated processing system and/or adistributed processing system.

Wireless device 102 may further includes a memory 82, such as forstoring local versions of applications being executed by processor 80.Memory 82 can include a type of memory usable by a computer, such asrandom access memory (RAM), read only memory (ROM), tapes, magneticdiscs, optical discs, volatile memory, non-volatile memory, and anycombination thereof.

Further, wireless device 102 includes a communications component 84 thatprovides for establishing and maintaining communications with one ormore parties utilizing hardware, software, and services as describedherein. Communications component 84 may carry communications betweencomponents on wireless device 102, as well as between wireless device102 and external devices, such as devices located across acommunications network and/or devices serially or locally connected towireless device 102. For example, communications component 84 mayinclude one or more buses, and may further include transmit chaincomponents and receive chain components associated with a transmitterand receiver, respectively, operable for interfacing with externaldevices.

Additionally, wireless device 102 may further include a data store 86,which can be any suitable combination of hardware and/or software, thatprovides for mass storage of information, databases, and programsemployed in connection with aspects described herein. For example, datastore 86 may be a data repository for applications not currently beingexecuted by processor 80.

Wireless device 102 may additionally include a user interface component88 operable to receive inputs from a user of wireless device 102 andfurther operable to generate outputs for presentation to the user. Userinterface component 88 may include one or more input devices, includingbut not limited to a keyboard, a number pad, a mouse, a touch-sensitivedisplay, a navigation key, a function key, a microphone, a voicerecognition component, any other mechanism capable of receiving an inputfrom a user, or any combination thereof. Further, user interfacecomponent 88 may include one or more output devices, including but notlimited to a display, a speaker, a haptic feedback mechanism, a printer,any other mechanism capable of presenting an output to a user, or anycombination thereof.

Wireless device 102 may further include a connection manager 10 operableto select one or more available networks for wireless device 102 toconnect with and send a connection request the selected network.

Referring now to FIG. 13, illustrated is an activation engine component106 operable within the connectivity system in accordance with yetanother aspect. Activation engine component 106 manages networkconnectivity matters for an access network. Activation engine component106 includes processor component 70 for carrying out processingfunctions associated with one or more of components and functionsdescribed herein. Processor component 70 can include a single ormultiple set of processors or multi-core processors. Moreover,processing component 70 can be implemented as an integrated processingsystem and/or a distributed processing system.

Activation engine component 106 further includes a memory 72, such asfor storing local versions of applications being executed by processorcomponent 70. Memory 72 can include random access memory (RAM), readonly memory (ROM), and a combination thereof.

Further, activation engine component 106 includes a communicationscomponent 34 that provides for establishing and maintainingcommunications with one or more parties utilizing hardware, software,and services as described herein. Communications component 34 may carrycommunications between components on activation engine 106, as well asbetween activation engine component 106 and external devices, such asdevices located across a communications network and/or devices seriallyor locally connected to activation engine 106.

Additionally, activation engine component 106 may further include a datastore 76, which can be any suitable combination of hardware and/orsoftware, that provides for mass storage of information, databases, andprograms employed in connection with aspects described herein. Forexample, data store 76 may be a data repository for applications notcurrently executing.

Activation engine component 106 may include a provisioning statusdatabase 22 which may determine whether a wireless device is alreadyprovisioned in an HLR. In addition, activation engine component 106 alsoinclude an HLR Manager Component 20 which may send provisioning messages24 and/or de-provisioning messages 26 to the HLR.

Referring now to FIG. 14, illustrated is a system 1400 configured tocontrol provisioning of a wireless communication device in a cellularnetwork. For example, system 1400 can reside at least partially within atransmitter, mobile device, etc. It is to be appreciated that system1400 is represented as including functional blocks, which can befunctional blocks that represent functions implemented by a processor,software, or combination thereof (e.g., firmware). System 1400 includesa logical grouping 1402 of electrical components that facilitatecontrolling provisioning of a wireless communication device in acellular network. For instance, logical grouping 1402 may includecomponent 1404 for maintaining, at a network component, a provisioningstatus database comprising status information corresponding toprovisioning in a home location register of one or more wirelesscommunication devices for one or more cellular networks. Further,logical grouping 1402 may comprise component 1406 for initiatingprovisioning or de-provisioning of a wireless communication device for acellular network in the home location register in response to atriggering event. Additionally, system 1400 can include a memory 1408that retains instructions for executing functions associated withelectrical components 1404 and 1406. While shown as being external tomemory 1408, it is to be understood that one or more of electricalcomponents 1404 and 1406 can exist within memory 1408.

Referring now to FIG. 15, illustrated is a system 1500 configured tocontrol provisioning of a wireless communication device in a cellularnetwork. For example, system 1500 can reside at least partially within atransmitter, mobile device, etc. It is to be appreciated that system1500 is represented as including functional blocks, which can befunctional blocks that represent functions implemented by a processor,software, or combination thereof (e.g., firmware). System 1500 includesa logical grouping 1502 of electrical components that facilitatecontrolling provisioning of a wireless communication device in acellular network. For instance, logical grouping 1502 may includecomponent 1504 for receiving, from a cellular network having a networkidentifier, a connection request for establishing a connection with awireless device. Further, logical grouping 1502 may comprise component1506 for determining provisioning data corresponding to a home locationregister (HLR) to enable connecting the wireless device to the cellularnetwork based on the network identifier, wherein the provisioning dataincludes a network entity identifier of a specific network entity in thecellular network to use for connecting with the wireless device. Inaddition, logical grouping 1502 may comprise component 1508 forproviding at least a portion of the provisioning data including thenetwork entity identifier to the cellular network. Additionally, system1500 can include a memory 1510 that retains instructions for executingfunctions associated with electrical components 1504, 1506 and 1508.While shown as being external to memory 1510, it is to be understoodthat one or more of electrical components 1504, 1506 and 1508 can existwithin memory 1510.

As used in this application, the terms “component,” “module,” “system”and the like are intended to include a computer-related entity, such asbut not limited to hardware, firmware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a computing device and the computing device can be a component. Oneor more components can reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate by way oflocal and/or remote processes such as in accordance with a signal havingone or more data packets, such as data from one component interactingwith another component in a local system, distributed system, and/oracross a network such as the Internet with other systems by way of thesignal.

Furthermore, various aspects are described herein in connection with aterminal, which can be a wired terminal or a wireless terminal Aterminal can also be called a system, device, subscriber unit,subscriber station, mobile station, mobile, mobile device, remotestation, remote terminal, access terminal, user terminal, terminal,communication device, user agent, user device, or user equipment (UE). Awireless terminal may be a cellular telephone, a satellite phone, acordless telephone, a Session Initiation Protocol (SIP) phone, awireless local loop (WLL) station, a personal digital assistant (PDA), ahandheld device having wireless connection capability, a computingdevice, or other processing devices connected to a wireless modem.Moreover, various aspects are described herein in connection with a basestation. A base station may be utilized for communicating with wirelessterminal(s) and may also be referred to as an access point, a Node B, orsome other terminology.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

The techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and othersystems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband-CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA system may implement a radio technology such as EvolvedUTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are partof Universal Mobile Telecommunication System (UMTS). 3GPP Long TermEvolution (LTE) is a release of UMTS that uses E-UTRA, which employsOFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTEand GSM are described in documents from an organization named “3rdGeneration Partnership Project” (3GPP). Additionally, cdma2000 and UMBare described in documents from an organization named “3rd GenerationPartnership Project 2” (3GPP2). Further, such wireless communicationsystems may additionally include peer-to-peer (e.g., mobile-to-mobile)ad hoc network systems often using unpaired unlicensed spectrums, 802.xxwireless LAN, BLUETOOTH and any other short- or long-range, wirelesscommunication techniques.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems may includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches may also be used.

The various illustrative logics, logical blocks, modules, and circuitsdescribed in connection with the embodiments disclosed herein may beimplemented or performed with a general purpose processor, a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but, in the alternative, the processor may be any conventionalprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Additionally, at least oneprocessor may comprise one or more modules operable to perform one ormore of the steps and/or actions described above.

Further, the steps and/or actions of a method or algorithm described inconnection with the aspects disclosed herein may be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module may reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a harddisk, a removable disk, a CD-ROM, or any other form of storage mediumknown in the art. An exemplary storage medium may be coupled to theprocessor, such that the processor can read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium may be integral to the processor. Further, in some aspects, theprocessor and the storage medium may reside in an ASIC. Additionally,the ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal. Additionally, in some aspects, the steps and/or actionsof a method or algorithm may reside as one or any combination or set ofcodes and/or instructions on a machine readable medium and/or computerreadable medium, which may be incorporated into a computer programproduct.

In one or more aspects, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored or transmitted as one or moreinstructions or code on a computer-readable medium. Computer-readablemedia includes both computer storage media and communication mediaincluding any medium that facilitates transfer of a computer programfrom one place to another. A storage medium may be any available mediathat can be accessed by a computer. By way of example, and notlimitation, such computer-readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, any connectionmay be termed a computer-readable medium. For example, if software istransmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs usually reproduce data optically withlasers. Combinations of the above should also be included within thescope of computer-readable media.

While the foregoing disclosure discusses illustrative aspects and/orembodiments, it should be noted that various changes and modificationscould be made herein without departing from the scope of the describedaspects and/or embodiments as defined by the appended claims.Furthermore, although elements of the described aspects and/orembodiments may be described or claimed in the singular, the plural iscontemplated unless limitation to the singular is explicitly stated.Additionally, all or a portion of any aspect and/or embodiment may beutilized with all or a portion of any other aspect and/or embodiment,unless stated otherwise.

1. A method of controlling provisioning of a wireless communicationdevice in a cellular network, comprising: maintaining, at a networkcomponent, a provisioning status database comprising status informationcorresponding to provisioning in a home location register of one or morewireless communication devices for one or more cellular networks; andinitiating provisioning or de-provisioning of a wireless communicationdevice for a cellular network in the home location register in responseto a triggering event.
 2. The method of claim 1, further comprising:receiving signaling corresponding to a request for the wirelesscommunication device to connect to the cellular network, wherein thesignaling includes a device identifier corresponding to the wirelesscommunication device and a network identifier corresponding to thecellular network, and wherein the signaling corresponding to the requestcomprises the triggering event.
 3. The method of claim 2, furthercomprising: determining from the status information in the provisioningstatus database, in response to the request and based on the deviceidentifier and the network identifier, that the wireless communicationdevice is not provisioned in the home location register; obtaining, froma master database having a plurality of provisioning data for aplurality of wireless communication devices, provisioning datacorresponding to the device identifier and the network identifier; andwherein initiating provisioning or de-provisioning comprisestransmitting a provisioning message destined for the home locationregister, wherein the provisioning message includes the provisioningdata and the device identifier.
 4. The method of claim 3, wherein theprovisioning message initiates creation in the home location register ofa provisioning record for the wireless communication device on thecellular network.
 5. The method of claim 1, further comprising:determining an occurrence of a de-provisioning condition, wherein theoccurrence of the de-provisioning condition comprises the triggeringevent.
 6. The method of claim 5, wherein initiating provisioning orde-provisioning comprises transmitting a de-provisioning messagedestined for the home location register, and wherein the de-provisioningmessage initiates removing from the home location register aprovisioning record comprising provisioning data for the wirelesscommunication device on the cellular network.
 7. The method of claim 5,wherein determining the occurrence of the de-provisioning conditioncomprises determining that a capacity for storing provisioning recordsin the home location register has reached a capacity threshold level. 8.The method of claim 5, wherein determining the occurrence of thede-provisioning condition comprises determining inactivity of thewireless communication device on the cellular network has reached aninactivity threshold level.
 9. The method of claim 5, whereindetermining the occurrence of the de-provisioning condition comprisesreceiving signaling corresponding to a request for the wirelesscommunication device to disconnect from the cellular network, whereinthe signaling includes a device identifier corresponding to the wirelesscommunication device and a network identifier corresponding to thecellular network.
 10. The method of claim 1, further comprising:receiving provisioning data for the wireless communication device; andtransmitting the provisioning data to a master database for storageuntil occurrence of the triggering event that causes initiating of theprovisioning at the home location register.
 11. The method of claim 10,further comprising: transmitting at least a portion of the provisioningdata to the wireless communication device in response to a provisioningdata query received from the wireless device.
 12. The method of claim 1,wherein the home location register is configured to store a plurality ofprovisioning data corresponding to a plurality of different networkcarriers.
 13. The method of claim 1, wherein the provisioning statusdatabase comprises a device identifier field and a network identifierfield.
 14. The method of claim 1, further comprising: receivingsubscription data corresponding to the wireless communication device.15. The method of claim 14, further comprising: storing, in a masterdatabase, the subscription data corresponding to the wirelesscommunication device.
 16. The method of claim 15, further comprising:receiving modified subscription data corresponding to the wirelesscommunication device; and storing, in the master database, the modifiedsubscription data corresponding to the wireless communication device.17. At least one processor configured to control provisioning of awireless communication device in a cellular network: a first module formaintaining, at a network component, a provisioning status databasecomprising status information corresponding to provisioning in a homelocation register of one or more wireless communication devices for oneor more cellular networks; and a second module for initiatingprovisioning or de-provisioning of a wireless communication device for acellular network in the home location register in response to atriggering event.
 18. A computer program product, comprising: acomputer-readable medium comprising: a first set of codes for causing acomputer to maintain, at a network component, a provisioning statusdatabase comprising status information corresponding to provisioning ina home location register of one or more wireless communication devicesfor one or more cellular networks; and a second set of codes for causingthe computer to initiate provisioning or de-provisioning of a wirelesscommunication device for a cellular network in the home locationregister in response to a triggering event.
 19. An apparatus,comprising: means for maintaining, at a network component, aprovisioning status database comprising status information correspondingto provisioning in a home location register of one or more wirelesscommunication devices for one or more cellular networks; and means forinitiating provisioning or de-provisioning of a wireless communicationdevice for a cellular network in the home location register in responseto a triggering event.
 20. An apparatus for controlling provisioning ofa wireless communication device in a cellular network, comprising: aprovisioning status database operable to maintain status informationcorresponding to provisioning in a home location register of one or morewireless communication devices for one or more cellular networks; and ahome location register manager component operable to initiateprovisioning or de-provisioning of a wireless communication device for acellular network in the home location register in response to atriggering event.
 21. The apparatus of claim 20, further comprising: anactivation engine operable to receive signaling corresponding to arequest for the wireless communication device to connect to the cellularnetwork, wherein the signaling includes a device identifiercorresponding to the wireless communication device and a networkidentifier corresponding to the cellular network, and wherein thesignaling corresponding to the request comprises the triggering event.22. The apparatus of claim 21, wherein the activation engine is furtheroperable to determine from the status information in the provisioningstatus database, in response to the request and based on the deviceidentifier and the network identifier, that the wireless communicationdevice is not provisioned in the home location register; and wherein theactivation engine is further operable to obtain, from a master databasehaving a plurality of provisioning data for a plurality of wirelesscommunication devices, provisioning data corresponding to the deviceidentifier and the network identifier.
 23. The apparatus of claim 22,wherein the home location manager component is further operable totransmit a provisioning message destined for the home location register,wherein the provisioning message includes the provisioning data and thedevice identifier.
 24. The apparatus of claim 23, wherein theprovisioning message initiates creation in the home location register ofa provisioning record for the wireless communication device on thecellular network.
 25. The apparatus of claim 20, further comprising anactivation engine operable to determine an occurrence of ade-provisioning condition, and wherein the occurrence of thede-provisioning condition comprises the triggering event.
 26. Theapparatus of claim 25, wherein the home location manager component isfurther operable to transmit a de-provisioning message destined for thehome location register, and wherein the de-provisioning messageinitiates removing from the home location register a provisioning recordcomprising provisioning data for the wireless communication device onthe cellular network.
 27. The apparatus of claim 25, wherein determiningthe occurrence of the de-provisioning condition comprises determiningthat a capacity for storing provisioning records in the home locationregister has reached a capacity threshold level.
 28. The apparatus ofclaim 25, wherein determining the occurrence of the de-provisioningcondition comprises determining inactivity of the wireless communicationdevice on the cellular network has reached an inactivity thresholdlevel.
 29. The apparatus of claim 25, wherein determining the occurrenceof the de-provisioning condition comprises receiving signalingcorresponding to a request for the wireless communication device todisconnect from the cellular network, wherein the signaling includes adevice identifier corresponding to the wireless communication device anda network identifier corresponding to the cellular network.
 30. Theapparatus of claim 20, further comprising: an activation engine operableto receive provisioning data for the wireless communication device andtransmit the provisioning data to a master database for storage untiloccurrence of the triggering event that causes initiating of theprovisioning at the home location register.
 31. The apparatus of claim30, wherein the activation engine is further operable to transmit atleast a portion of the provisioning data to the wireless communicationdevice in response to a provisioning data query received from thewireless device.
 32. The apparatus of claim 20, wherein the homelocation register is configured to store a plurality of provisioningdata corresponding to a plurality of different network carriers.
 33. Theapparatus of claim 20, wherein the provisioning status databasecomprises a device identifier field and a network identifier field. 34.The apparatus of claim 20, further comprising: an activation engineoperable to receive subscription data corresponding to the wirelesscommunication device.
 35. The apparatus of claim 34, wherein theactivation engine is further operable to store, in a master database,the subscription data corresponding to the wireless communicationdevice.
 36. The apparatus of claim 35, wherein the activation engine isfurther operable to receive modified subscription data corresponding tothe wireless communication device and store, in the master database, themodified subscription data corresponding to the wireless communicationdevice.
 37. A method of controlling provisioning of a wirelesscommunication device in a cellular network, comprising: receiving, froma cellular network having a network identifier, a connection request forestablishing a connection with a wireless device; determiningprovisioning data corresponding to a home location register (HLR) toenable connecting the wireless device to the cellular network based onthe network identifier, wherein the provisioning data includes a networkentity identifier of a specific network entity in the cellular networkto use for connecting with the wireless device; and providing at least aportion of the provisioning data including the network entity identifierto the cellular network.
 38. The method of claim 37, wherein theconnection request further comprises a wireless device identifier, andwherein determining the provisioning data is further based on thewireless device identifier.
 39. The method of claim 37, wherein thenetwork entity identifier identifies a local network specific gatewaynode in the cellular network that is defined for providing services forwireless devices provisioned to the HLR.
 40. At least one processorconfigured to control provisioning of a wireless communication device ina cellular network: a first module for receiving, from a cellularnetwork having a network identifier, a connection request forestablishing a connection with a wireless device; and a second moduledetermining provisioning data corresponding to a home location register(HLR) to enable connecting the wireless device to the cellular networkbased on the network identifier, wherein the provisioning data includesa network entity identifier of a specific network entity in the cellularnetwork to use for connecting with the wireless device; and a thirdmodule for providing at least a portion of the provisioning dataincluding the network entity identifier to the cellular network.
 41. Acomputer program product, comprising: a computer-readable mediumcomprising: a first set of codes for causing the computer to receive,from a cellular network having a network identifier, a connectionrequest for establishing a connection with a wireless device; a secondset of codes for causing the computer to determine provisioning datacorresponding to a home location register (HLR) to enable connecting thewireless device to the cellular network based on the network identifier,wherein the provisioning data includes a network entity identifier of aspecific network entity in the cellular network to use for connectingwith the wireless device; and a third set of codes for causing thecomputer to provide at least a portion of the provisioning dataincluding the network entity identifier to the cellular network.
 42. Anapparatus, comprising: means for receiving, from a cellular networkhaving a network identifier, a connection request for establishing aconnection with a wireless device; means for determining provisioningdata corresponding to a home location register (HLR) to enableconnecting the wireless device to the cellular network based on thenetwork identifier, wherein the provisioning data includes a networkentity identifier of a specific network entity in the cellular networkto use for connecting with the wireless device; and means for providingat least a portion of the provisioning data including the network entityidentifier to the cellular network.
 43. An apparatus for controllingprovisioning of a wireless communication device in a cellular network,comprising: a receiver operable to receive, from a cellular networkhaving a network identifier, a connection request for establishing aconnection with a wireless device; an activation engine operable todetermine provisioning data corresponding to a home location register(HLR) to enable connecting the wireless device to the cellular networkbased on the network identifier, wherein the provisioning data includesa network entity identifier of a specific network entity in the cellularnetwork to use for connecting with the wireless device; and to provideat least a portion of the provisioning data including the network entityidentifier to the cellular network.
 44. The apparatus of claim 43,wherein the connection request further comprises a wireless deviceidentifier, and wherein determining the provisioning data is furtherbased on the wireless device identifier.
 45. The apparatus of claim 43,wherein the network entity identifier identifies a local networkspecific gateway node in the cellular network that is defined forproviding services for wireless devices provisioned to the HLR.